Publish the Release A transition archive - #167
Merged
Merged
Conversation
myobie
force-pushed
the
fix/release-a-transition-archive
branch
from
September 5, 2026 04:00
a40ee25 to
4748ae5
Compare
myobie
force-pushed
the
fix/release-a-transition-archive
branch
from
September 5, 2026 04:07
4748ae5 to
dcb858e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release A must be readable by the deployed 0.2.1+48208e4 updater.
This change packages exactly one fabric member. Step 7 will restore paired packaging after Release A reaches every machine.
The plan records both production rollback exercises, the deployed reader clean-refusal proof, and the real recovery routes. The code comment no longer assumes that an open SSH port gives the recovery actor a working login.
Proof:
No tag, release, or deployment is part of this pull request.